common/memory: fix an XSM error path
authorJan Beulich <jbeulich@suse.com>
Mon, 19 Jan 2015 10:59:05 +0000 (11:59 +0100)
committerJan Beulich <jbeulich@suse.com>
Mon, 19 Jan 2015 10:59:05 +0000 (11:59 +0100)
XENMEM_{in,de}crease_reservation as well as XENMEM_populate_physmap
return the extent at which failure was detected, not error indicators.

Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Acked-by: Tim Deegan <tim@xen.org>
xen/common/memory.c

index 234dae62fec10e753a45a5bcebf398dd19ff3277..e84ace99a54087a465d1826883caaaa57b716b52 100644 (file)
@@ -747,11 +747,10 @@ long do_memory_op(unsigned long cmd, XEN_GUEST_HANDLE_PARAM(void) arg)
             return start_extent;
         args.domain = d;
 
-        rc = xsm_memory_adjust_reservation(XSM_TARGET, current->domain, d);
-        if ( rc )
+        if ( xsm_memory_adjust_reservation(XSM_TARGET, current->domain, d) )
         {
             rcu_unlock_domain(d);
-            return rc;
+            return start_extent;
         }
 
         switch ( op )